home *** CD-ROM | disk | FTP | other *** search
-
- NETGROUP(5) UNIX Programmer's Manual NETGROUP(5)
-
- NNAAMMEE
- nneettggrroouupp - defines network groups
-
- SSYYNNOOPPSSIISS
- nneettggrroouupp
-
- DDEESSCCRRIIPPTTIIOONN
- The nneettggrroouupp file specifies ``netgroups'', which are sets of ((hhoosstt,, uusseerr,,
- ddoommaaiinn)) tuples that are to be given similar network access.
-
- Each line in the file consists of a netgroup name followed by a list of
- the members of the netgroup. Each member can be either the name of an-
- other netgroup or a specification of a tuple as follows:
-
- (host, user, domain)
- where the hhoosstt, uusseerr, and ddoommaaiinn are character string names for the cor-
- responding component. Any of the comma separated fields may be empty to
- specify a ``wildcard'' value or may consist of the string ``-'' to speci-
- fy ``no valid value''. The members of the list may be separated by
- whitespace; the ``\'' character may be used at the end of a line to spec-
- ify line continuation. The functions specified in getnetgrent(3) should
- normally be used to access the nneettggrroouupp database.
-
- These functions operate on the db version of the nneettggrroouupp ((nneettggrroouupp..ddbb))
- file which can be generated using netgroup_mkdb. If that file is not
- present, and the system supports NNIISS,, then the nneettggrroouupp NNIISS maps are
- used. The NNIISS maps are also used if the nneettggrroouupp file contains a ++ entry.
-
- Lines that begin with a # are treated as comments.
-
- FFIILLEESS
- /etc/netgroup.db the netgroup database.
-
- SSEEEE AALLSSOO
- netgroup_mkdb(8), getnetgrent(3), exports(5)
-
- CCOOMMPPAATTIIBBIILLIITTYY
- The file format is compatible with that of various vendors, however it
- appears that not all vendors use an identical format.
-
- BBUUGGSS
- The interpretation of access restrictions based on the member tuples of a
- netgroup is left up to the various network applications.
-
- BSD Experimental December 11, 1993 1
-